-
Notifications
You must be signed in to change notification settings - Fork 39
refactor: update generate translations #5682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-angelopolis canceled.
|
✅ Deploy Preview for bloom-flagly canceled.
|
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-angelopolis ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-flagly ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for partners-bloom-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
YazeedLoonat
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good minor suggestion but non blocking
✅ Deploy Preview for bloom-public-seeds ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-exygy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for bloom-lakeview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Description
Updates our generate machine translations script to make it easier - previously we needed to first run the missing translations script, then manually add each language one by one into a CSV and pass it into the machine translations script. Now this script does both.
In development, you can just add the English keys in the general file and then run this script.
Hoping this will help our translations dev efficiency!
How Can This Be Tested/Reviewed?
There are instructions in the file, but add the google translate keys, and from within the shared-helpers script folder run
ts-node generate-machine-translations.ts > translated-strings.json.You'll need to manually remove some non-English keys to see the appropriate output.
I will update the existing Notion docs for these scripts post-merge.
Author Checklist:
yarn generate:clientand/or created a migration when requiredReview Process: